canon/tiers/01_Tier_1_Foundation/T1_Tier_C_MMO_Spec [ACTIVE v1.0].md
RULED ADDENDUM POINTER (2026-07-26; INTEGRATED July 27, 2026): docs/COMBAT_PROGRAM_ADDENDUM.md
§12 is Josh's ruled canon and binds this doc through THE MMO BRIDGE — the same role, stat, and
build architecture that drives single-player companion party building scales into Tier C group
and raid play and into the canonical 100-player World Boss. Where it landed here — the raid-role
taxonomy at §8.7; the recovered four-team World Boss operational architecture and adaptive boss
AI at §8.8; the party-as-training-ground and build-breadth discipline at §8.9. Touchpoints at
§1.2, §1.3, §2.2, §8.3, §14.3, and §15. Held elsewhere by authority — the role and build axes
and the build-space sweeps at T1\_Combat\_System\_Spec and T1\_Ability\_Tree; companion and
familiar stat spreads, the ally-intelligence axis, loadout parity, and investment protection at
T1\_Integrity\_Paths\_Worldstates\_Master §8.11; the six-attribute progression at
T1\_Ability\_Tree.
Last updated: July 27, 2026\.
Tier 1 Foundation. Loaded by Project 1 Foundation Reference for canon questions, Project 5 UE5 for Tier C build pipeline integration, Project 6 Music for Tier C boss themes and regional vril substrate music cues, Project 7 Art for Tier C visual asset variation. Project 4 Quest Writing loads on Tier C SQ generation queries.
Drive placement: /Humanity/01-Foundation/T1\_Tier\_C\_MMO\_Spec.
This doc owns the canonical Tier C MMO architecture. Authority covers three-tier architecture scope clarification, Tier C scope by exclusion, scale-of-impact framework, guild integrity calculation, regional substrate shaping mechanics, Tier C World Boss canonical separation from Tier A chapter-level Boss encounters, competitive multiplayer modes architecture, territory control framework, guild systems framework, player-driven economy framework, Magus mastery tier Tier C architecture (Tier C side; per-capability content authority distributes per CVD §12.1), Tier C SQ infinite generation framework, the Tier C raid-role taxonomy as the group-arena reading of the canonical build-role axes, and the World Boss operational-team architecture with its adaptive boss AI.
Per-region Tier C content authoring lives in Tier 8 region pages at Phase 7+ post Tier A complete per CVD §1 build sequence. Tier B catalog content lives in T1\_Tier\_B\_DLC\_Catalog (populate target post-cascade phase per T1\_Architecture\_and\_State). Per-capability Magus initiation questline content lives in T1\_Combat\_System\_Spec, T1\_Trades\_Master, T1\_Ability\_Tree per CVD §12.1 detail pointer. Numerical specifications for engagement floors, calculation thresholds, calibration parameters defer to Tier C build phase calibration. Server architecture engineering specifics live in Project 5 UE5 Tier C scope. Solo region layer content lives in T1\_Story\_Spine plus Tier 2 ChapterDesign briefs (Tier A canonical 77-chapter campaign). The build machinery the raid-role taxonomy at §8.7 reads is owned upstream and cross-referenced here, never restated: the role and build axes, the selectable minor and major bonus pools, loadout sets, spec purposes, the rarity ladder through LEGENDARY and MYTHIC, and the build-space sweeps live at T1\_Combat\_System\_Spec and T1\_Ability\_Tree; the six-attribute progression lives at T1\_Ability\_Tree; companion and familiar loadout parity, investment protection, player-shaped ally stat spreads, and the ally-intelligence axis live at T1\_Integrity\_Paths\_Worldstates\_Master §8.11. This doc owns only the Tier C group-arena reading of that architecture.
Type A structured plus Type B prose hybrid. Canonical framework specifications use structured field language; architectural commentary uses prose. No header-body separator (single-doc unified read for narrative consumers and validation consumers). Section-anchor-stable retrieval via H2/H3/H4 markdown convention.
Concept-lock at v1.0 May 10, 2026\. Version bumps follow T1\_Architecture\_and\_State Doc Naming Convention rules. Numerical calibration during Tier C build phase produces v1.1 minor edits; canonical architecture changes produce v2.0 major rebuilds. Drive-title-only version stamping per the v2.x discipline noted in T1\_Architecture\_and\_State.
20-30 pages at concept-lock v1.0. Numerical calibration during Tier C build phase expands to 40-60 pages at v2.0 production state.
---
T1\_Tier\_C\_MMO\_Spec consumes CVD canonical foundation across multiple sections.
CVD §1 establishes the three-tier architecture (Tier A Solo Base, Tier B Solo DLC, Tier C MMO) and the 10-year build sequence (Tier A then Tier B then Tier C). CVD §13 owns the World Boss and MMO Layer Vision: §13.1 World bosses as collective-action endpoints, §13.2 Collective action shapes regional substrate, §13.3 Scale-of-impact framework, §13.4 Tier B DLC interaction with Tier C, §13.5 What Tier C MMO does not change. CVD §11.4 Infinite SQ generation principle binds Tier C SQ canonical extension. CVD §17.5 Mastery framework hard line binds Magus tier Tier C MMO endgame engagement requirement. CVD §17.4 Integrity hard lines confirm path-agnostic content discipline (evil-state and good-state equally weighted in production scope). CVD §6 cultural depiction standard applies in Tier C identically to Tier A. CVD §17.1 cultural depiction hard lines bind Tier C content per the universal canonical discipline.
T1\_Integrity\_Paths\_Worldstates\_Master v2.0 owns the 5-band integrity framework (L1 Truly Good, L2 Good Enough, L3 Drifting, L4 Evil, L5 Pure Evil terminal) consumed for guild integrity classification and individual integrity throughout Tier C interactions. T1\_Combat\_System\_Spec v1.0 owns Tier A 5 chapter-level Boss encounters (Ch 8, Ch 23 or Ch 25, Ch 38, Ch 55, Ch 65\) explicitly distinct from Tier C World Boss roster owned here. T1\_Vril\_and\_Magic\_System\_Master v2.0 owns vril substrate physics consumed by Tier C regional vril modulation. T1\_World\_Geography\_Master v2.0 owns canonical 77-chapter region roster against which Tier C scope-by-exclusion calculates. T1\_Trades\_Master v1.0 and T1\_Ability\_Tree own per-capability Magus initiation questline content per CVD §12.1 detail pointer. T1\_Integrity\_Paths\_Worldstates\_Master §8.11 additionally owns the single-player companion and familiar build architecture — loadout parity with the protagonist, investment protection on departure, player-shaped ally stat spreads, and the ally-intelligence behavior-quality axis — consumed here at §8.7 through §8.9 as the training-ground layer beneath Tier C raid roles. T1\_Combat\_System\_Spec and T1\_Ability\_Tree own the endgame build-role taxonomy and the build-space sweeps that the Tier C raid-role reading at §8.7 crosses into group scale; T1\_Ability\_Tree owns the canonical six-attribute progression that both arenas read. T1\_Tier\_B\_DLC\_Catalog owns the Tier B pre-identified region catalog when populated; current Tier B exemplar list inline at §4.2 pending populate.
T0\_Boss\_Encounter scope-locked registry consumes Tier C World Boss canonical roster framework when Tier C build phase opens. T0\_Antagonist\_Network\_Registry consumes Tier C antagonist operational manifestation framework. T0\_Quest\_Seed\_Registry consumes Tier C SQ infinite generation seed templates. T0\_Cross\_Cultural\_Link\_Graph consumes documented-cultural-substrate template framework for Tier C SQ generation provenance. T0\_Source\_Material\_Registry per Pipeline §8 routes Tier C SQ documented-source provenance.
T1\_Build\_Pipeline\_Contracts v1.0 ACTIVE consumer interfaces. Pipeline §1 UE5 consumes Tier C MMO server architecture, shared-instance world layer specification, regional substrate state machine. Pipeline §6 Quest Writing consumes Tier C SQ infinite generation framework with batch-level cultural authenticity audit per §6.8. Pipeline §7 Region Page Build consumes Tier C scope determination per §4 of this doc; affects per-region build pipeline routing. Pipeline §3 AIVA consumes Tier C World Boss themes and regional vril substrate music cues. Pipeline §4 ElevenLabs consumes Tier C NPC voice assignment with regional biography variation per §7.2. Pipeline §10 SFX consumes Tier C ambient audio variation per regional substrate state.
---
The canonical 77-chapter campaign. Single-player. Fully authored. The 30-million-word backbone of the game. Every chapter of the main story, every trade questline, every side questline, every weapon, familiar, creature, ability, and inscription anchor lives in Tier A canon.
Tier A operates through the solo region layer — every player has their own private-instance copy of the game world, permanently and uniquely shaped by their choices. Tier A players experience canonical-state regional substrate per CVD §13.2. The Tier A 77-chapter solo arc is the canonical foundation; Tier B and Tier C extend the experience without altering Tier A canon.
Tier A players can earn Magister Templi (Tier 9\) in any developable capability via the post-Ch 77 prestige questline per CVD §17.5. Tier A solo path caps at Magister Templi. Magus tier (Tier 10\) requires Tier C MMO engagement per §12 of this doc.
Pre-identified story-significant regions held off-limits to MMO player-shaping per CVD §13.4. Authored with Tier A canonical discipline, released post-base-game. Tier B regions retain canonical-state substrate regardless of nearby Tier C MMO guild influence.
Tier B catalog ownership rests with T1\_Tier\_B\_DLC\_Catalog. Current canonical Tier B catalog exemplar reference at §4.2 of this doc pending T1\_Tier\_B\_DLC\_Catalog populate (post-cascade phase target per T1\_Architecture\_and\_State). Tier B catalog can grow during pre-cascade phase; boundary updates trigger Tier C scope recalculation per §4.4.
The rest of Earth. Documented cultures present, no protected narrative; collective player action shapes regional vril, NPC biographies, and world state under guild integrity influence per CVD §13.2.
Tier C MMO is optional. Tier A Solo Base is complete in itself. A solo player completing the base game never encounters a world boss as required content per CVD §13.1. A player who has never completed Chapter 1 can participate in Tier C World Bosses, territory control, and competitive PvP. A player who has completed all 77 chapters may never engage with Tier C. Both paths are valid complete experiences.
Tier C extends the world that exists outside the canonical narrative — populated by documented cultures, available for collective player action that shapes regional substrate. Tier C is the path to Magus mastery tier per CVD §17.5 hard line.
Per CVD §13.5 canonical:
Tier B catalog regions retain Tier A canonical-state substrate regardless of guild influence per §3.2. Off-Earth canonical Hard Line chapters (Atlantis Ch 66, Pohjola Ch 67, the Apsu Ch 68, the Duat Ch 69\) are inherently outside Tier C scope.
---
Tier C scope equals all Earth real-world regions minus regions covered by Tier A canonical 77 chapters per T1\_World\_Geography\_Master minus Tier B catalog per T1\_Tier\_B\_DLC\_Catalog.
The exclusion rule operationalizes CVD §13 canon. T1\_Tier\_C\_MMO\_Spec does not enumerate Tier C regions exhaustively; Tier C scope is defined by exclusion against Tier A and Tier B explicit canonical rosters.
T1\_Tier\_B\_DLC\_Catalog is the canonical authority. Current canonical Tier B catalog roster exemplar pending populate:
This 10-region exemplar list serves as canonical reference pending T1\_Tier\_B\_DLC\_Catalog populate at post-cascade phase. Tier B catalog can grow during pre-cascade phase per §4.4 boundary update discipline.
Atlantis Ch 66, Pohjola Ch 67, the Apsu Ch 68, the Duat Ch 69 are canonical mythological-realm chapters not anchored to Earth real-world geography. These chapters are inherently outside Tier C scope (not Earth-region playable). Solo Tier A access only via the canonical mythological-realm progression.
Earth-anchored canonical Hard Line chapters (Ch 8 Swahili Coast, Ch 29 Sámi, Ch 38 Azores, Ch 42 Haiti, Ch 55 Atacama, Ch 57 Australia, Ch 58 Antarctica, Ch 65 Antarctica Return, Ch 74 Velheim) retain Tier A canonical-state substrate. CVD §13.5 cites Ch 38, Ch 57, Ch 69 as exemplars; the canonical principle covers the full hard-line spine.
Tier C scope updates trigger from Tier B catalog updates only. T1\_Tier\_B\_DLC\_Catalog can grow during pre-cascade phase as additional pre-identified story-significant regions surface through canonical authoring; each addition removes the corresponding region from Tier C scope. Tier A 77-chapter region roster is locked at canonical foundation and does not change post-restructure.
Boundary update protocol: T1\_Tier\_B\_DLC\_Catalog amendment triggers T1\_Tier\_C\_MMO\_Spec §4.2 inline reference patch. Tier C scope automatically recalculates by exclusion. No standalone Tier C region roster maintenance required.
---
Per CVD §13.3 canonical. Three impact scales operate in Tier C MMO. The scale-of-impact is itself a Layer 3 substrate routing per CVD §13.3 — the scale at which collective action shifts substrate is an in-game canonical truth. Guild integrity is metaphysical-real, not just statistical-aggregate.
Personal arc impact only. Modulates own biography state and immediate-vicinity NPC reactions. Does not shape regional substrate.
Solo guildless player can engage Tier C content — PvP encounters, World Boss participation as 1-of-100 contribution, exploration of Tier C regions, competitive multiplayer mode participation, Tier C SQ engagement. Solo engagement permitted; solo regional substrate shaping prohibited per canonical principle.
Solo Tier A players engaging Tier C content remain at solo scale. Tier C engagement does not require guild membership for participation; guild membership is required for regional substrate shaping per §5.2.
Regional impact. Guild aggregate integrity per §6 calculation shapes guild-controlled regional substrate per §7. Regional substrate shaping authority gates at guild collective scale.
Guild scale operates through territorial control mechanic per §10. Guilds establish territorial control through the four-phase canonical sequence. Territorial control regions become guild-influenced regional substrate per §7 mechanics. Loss of territorial control to a competing faction restores canonical-state substrate for the contested region.
Continental and world impact. Aggregate cross-guild integrity patterns shape continental-scale phenomena. Server scale phenomena are rare, mechanically discrete, and surface in canonical world events.
Server collective shifts manifest at canonical thresholds — global vril restoration meter advancement, continental-scale environmental anomaly emergence, server-wide world event triggering. Threshold calibration defers to Tier C build phase.
The three impact scales canonically reflect substrate-shifting authority in the game world. CVD §2 core thesis (consciousness as substrate) routes through scale-of-impact: individual consciousness shapes individual experience; collective consciousness shapes collective experience; substrate responds to consciousness density. Guild integrity is metaphysical-real per CVD §13.3 — the canonical principle is in-game-true, not metafictional commentary on multiplayer scale.
---
Guild integrity equals the mean of integrity scores across guild members active within rolling 30-day window.
Calculation: sum of integrity scores of qualifying members divided by qualifying member count. The arithmetic mean preserves every active member's canonical contribution while preventing large-guild dominance through summation.
The 30-day rolling window canonical principle: active engagement is the substrate-shifting prerequisite. Inactive accounts do not carry weight per the canonical "collective action" framing of CVD §13.2.
Guild member qualifies for guild integrity calculation when the member has engaged Tier C content within the rolling 30-day window. Qualifying engagement: Tier C login plus any of PvP participation, World Boss participation, territorial action, Tier C SQ engagement, or regional substrate interaction.
Threshold calibration defers to Tier C build phase. The canonical principle locks at v1.0: active-engagement gating preserves the canonical "collective action" substrate-shifting framing.
Guild integrity reads as one of the five canonical bands per CVD §9.2 plus T1\_Integrity\_Paths\_Worldstates\_Master:
Numerical thresholds match individual integrity bands per T1\_Integrity\_Paths canonical authority. Guild classification updates each calculation refresh cycle per §6.4.
Guild integrity recalculates daily at canonical reset boundary. The rolling 30-day window slides forward daily. Newly qualifying members enter calculation at next refresh; members falling out of activity threshold drop at next refresh.
Specific reset cadence calibration (UTC reset versus regional reset, exact recalculation interval) defers to Tier C build phase.
Guild integrity classification does not gate access to canonical Tier C content per CVD §17.4 evil-and-good-equally-weighted production scope. Pure Evil guilds (L5) access Tier C World Bosses, territory control, competitive multiplayer modes, and Magus mastery tier prerequisite engagement identically to Truly Good guilds (L1). Path-specificity surfaces in canonical content variation (regional substrate shaping per §7 differs by guild integrity band) not in unlock or access.
The path-agnostic discipline preserves canonical CVD §17.4 hard line. Operational coldness, regional vril corruption, and NPC fearful biography variation in L4-L5 guild-controlled regions are canonical content surfaces, not access gates.
---
Per CVD §13.2 canonical. Guild integrity shapes three substrate domains in guild-controlled regions: regional vril, NPC biographies, world state. Solo Tier A players experience canonical-state regional substrate. Tier C MMO players experience guild-influenced regional substrate.
Guild-controlled regions accumulate integrity-correlated vril substrate texture per CVD §13.2.
L1 Truly Good guild presence increases regional vril clarity. Vril sites in guild territory exhibit enhanced recharge rate, clearer substrate perception at canonical Vril Sight thresholds, vril-positive ambient texture detectable through Inscription Adeptus Minor and above.
L5 Pure Evil guild presence introduces vril-corruption substrate. Vril sites in guild territory exhibit corrupted recharge texture, vril-negative ambient texture, increased negative consciousness manifestation rate. Vril corruption is canonical substrate response to integrity, not narrator declaration.
L2 through L4 guild integrity bands produce graduated vril texture between L1 clarity and L5 corruption. Specific modulation calibration defers to Tier C build phase.
Tier C NPCs in guild-influenced regions carry biographies modulated by guild integrity profile. Canonical biography variation domains:
NPC biography variation operates at framework level here. Per-NPC content authoring lives in Tier 8 region pages plus Project 4 Quest Writing per Tier C SQ infinite generation. Cultural depiction standard per CVD §6 binds all NPC biography variation regardless of guild integrity influence.
Regional events, weather, encounter spawn rates, and environmental anomalies modulate per guild integrity influence. Canonical world state domains in guild-controlled regions:
Specific modulation calibration defers to Tier C build phase. Canonical principle locks at v1.0.
Tier B catalog regions retain canonical-state substrate regardless of nearby Tier C MMO guild influence per CVD §13.4. Guild integrity shaping does not propagate into Tier B regions. Tier B regions experience as Tier A canonical-state by all visiting players, regardless of guild membership.
Earth-anchored canonical Hard Line chapters per CVD §17.11 hard-line spine retain Tier A canonical-state substrate. Guild integrity shaping does not propagate into these regions. Per CVD §13.5 the canonical principle covers the full hard-line spine, not only the §13.5 cited exemplars.
---
Per CVD §13.1 canonical, two boss scales operate in the game architecturally distinct from one another:
The two scales operate at architecturally distinct authoring layers, encounter sizes, and canonical content separation. Tier A chapter-level Bosses are not Tier C World Bosses; Tier C World Bosses are not Tier A chapter-level Bosses. The separation is canonical.
Tier C World Bosses are 100-player encounters at canonical Tier C spawn locations. Solo player completing Tier A Solo Base never encounters a Tier C World Boss as required content. Tier C World Bosses are the endpoint of guild-scale collective action: specific boss encounters that require coordinated 100-player engagement, with mechanics that scale to that engagement size.
100 players organize into four operational teams per Tier C World Boss encounter. Team composition is canonical at framework level; per-encounter team optimization emerges through player community innovation per §8.5.
Team composition adapts per Tier C World Boss specifics. Per-boss team requirements canonical at per-boss authoring level; framework operates here. The recovered operational-team architecture at §8.8 carries the pre-restructure authored partition of these same four functions with its seed team sizes and the adaptive boss AI; §8.7 carries the raid-role taxonomy the teams are staffed from.
Defeating a Tier C World Boss produces permanent regional improvements that benefit every player on the server, not only encounter participants. Canonical kill benefits:
Kill benefit canonical principle: server-collective action manifests at server-collective benefit. Per CVD §13.3 server collective scale, Tier C World Boss kill is a canonical substrate-shifting event.
Two servers may develop different strategies for the same Tier C World Boss. The canonical framework allows player community innovation. Tier C World Boss mechanics are documented at canonical depth; specific tactical solutions are not gated to a single intended approach.
The per-server strategy variation is itself canonical — collective intelligence shapes encounter resolution per CVD §13.3 server collective scale. Player community emergence is in-game canonical, not metafictional commentary on multiplayer dynamics.
Tier C World Boss canonical roster authors during Phase 6+ alongside Tier C build phase per CVD §1 build sequence (post Tier A complete). Tier C World Boss content draws on documented regional mythological and historical content per the canonical cultural depiction standard.
T0\_Boss\_Encounter scope-locked registry consumes Tier C World Boss canonical roster framework. Per-region Tier C World Boss content placement maps to Tier 8 region pages during Project 3 Region Building per Tier C scope determination per §4. Specific Tier C World Boss roster, per-boss mechanics, and regional placement detail authoring defers to Phase 6+ build cascade.
Per docs/COMBAT\_PROGRAM\_ADDENDUM.md §11 and §12 canonical (RULED, Josh 2026-07-26). Tier C group and raid play runs on the same build-role taxonomy as single-player party building. One taxonomy, two arenas — the group roles apply once to the companion party in Tier A and once to the guild raid in Tier C, and the architecture is designed once rather than twice.
The taxonomy itself is owned by T1\_Combat\_System\_Spec and T1\_Ability\_Tree and is read here at group scale. The enumeration that follows is a non-authoritative echo carried for legibility at Tier C scope; where it and the owning docs differ, the owning docs govern, and the echo follows them on every expansion. Its shape: six role axes — group support, group heals, group damage, single-target support, single-target heals, single-target damage — crossed with the build axes, which are mastery builds and their multi-mastery hybrids, per-weapon-class builds across the canonical 72, elemental builds with their element-combination and hybrid-element variants, and custom-forge builds assembled from merged spells at multi-mastery. The enumerations are the canonical seed set; expansion per encounter class and per Tier C content wave authors against the owning docs rather than against this section.
Tier C reads the taxonomy with four canonical properties.
The canonical 100-player World Boss per CVD §13.1 carries a pre-restructure authored operational architecture recovered into Tier C framework scope. The source of the operational detail — the four operational teams with their headcounts and the adaptive boss AI — is docs/original\_predclaude/extracted/GDD\_Humanity\_Game\_Complete.md §10.3 World Boss Design and §13.1 World Boss System — Full Detail, where the team roster, the per-team headcounts, and the learning-and-reset AI behavior are authored. The routing record is docs/original\_predclaude/INGEST\_GDD.md §13, which classes the world-boss four-team architecture and the adaptive boss AI as recovered detail whose home is this doc. The recovered content is Josh's own pre-Claude source and is recovered faithfully; it contradicts no locked canon.
Four operational teams, with the authored seed headcounts:
Headcounts are the authored seed values whose ranges bracket the canonical 100-player encounter; exact allocation, per-team floors, and per-boss variation calibrate at Tier C build phase per §1.5. The team roster is the seed architecture and expands per World Boss as the roster authors at Phase 6 and beyond per §8.6.
Adaptive boss AI is canonical at framework level. The boss learns mid-fight, weighting successful attack patterns upward and failed patterns downward, and it responds to terrain changes made by the Environmental Manipulation team, so the environmental lane is a genuine input to boss behavior rather than a cosmetic layer. The AI resets completely on respawn, so every encounter is adapted to fresh rather than solved once. This is the mechanical root of the §8.5 per-server strategy canon: the boss adapts within a fight and forgets between fights, which makes community innovation a continuous requirement rather than a single discovery. Learning rates, weighting magnitudes, and reset scope calibrate at Tier C build phase.
Reconciliation with the §8.3 framework. The two rosters describe the same four functions at different cut lines. Environmental Manipulation carries the terrain and battlefield-control function of §8.3 Team 3 Environmental and Tactical. Combat Core seats together the functions §8.3 splits across Team 1 Primary Combat and Team 2 Support and Sustain. Spawnling Management raises the add-control function folded into §8.3 Team 3 to a team of its own at the largest headcount in the encounter. Enhancement and Protection matches §8.3 Team 4 in name and function. The §8.3 framework-level statement stands unchanged and is not overwritten here; this section carries the authored operational instance, its seed headcounts, and the adaptive-AI behavior. Which cut line a given World Boss ships is a per-boss authoring decision under the §8.3 adapt-per-boss allowance, and the framework-level reconciliation of the two rosters is registered for Tier C build phase resolution.
Per docs/COMBAT\_PROGRAM\_ADDENDUM.md §12 canonical (RULED, Josh 2026-07-26). The single-player companion party is the training ground for Tier C raid building. A player who has spent the Tier A arc choosing an ally's stat spread, balancing intelligence against the combat attributes, and composing a party around their own specification has already practised what raid composition asks for. The transfer is designed rather than incidental — one role, stat, and build architecture, authored once and read at both arena sizes.
The single-player side of the architecture is owned by T1\_Integrity\_Paths\_Worldstates\_Master §8.11.6 through §8.11.10: companion loadout and bonus parity with the protagonist, investment protection on departure, player-shaped ally stat spreads over the canonical six-attribute roster, and the ally-intelligence axis where intelligence buys pattern detection, proactivity, and awareness at the cost of combat attributes. This doc consumes that architecture and does not restate it.
Three canonical properties of the bridge.
Balance measurement extends to Tier C. The build-space sweeps that Phase 5M and 5H own per docs/COMBAT\_PROGRAM\_ADDENDUM.md §10 include group-scale encounter classes: viability breadth is counted per raid-role axis, and a raid role that only one build can serve is a balance defect of the same class as a never-picked bonus pool. The AAAAA balance doctrine binds Tier C directly — mathematically overpowered builds are allowed, meta-collapse is the banned failure mode, and the target is many roles and strategies with hundreds to thousands of equally viable builds. Tier C carries the highest meta-collapse pressure of any arena because server communities converge on shared solutions, so the two canonical counterweights are the per-server strategy variation at §8.5, which keeps solutions plural across servers, and the sweeps, which measure whether the plurality is real. Calibration and sweep thresholds defer to Phase 5M and 5H; the doctrine locks here.
---
Three competitive multiplayer modes operate on the Tier C MMO layer.
The Vril Vessel functions as the flag. Every Capture the Flag map is based on a real ancient site from the game's geographic journey — documented archaeological or sacred sites adapted for competitive multiplayer at canonical cultural depiction standard per CVD §6.
The Vessel carrier gains a vril boost while carrying the Vessel. The carrier becomes a visible beacon — partial cloaking is possible, but the Vessel emits a subtle luminance that counters full cloaking. Astral Projection scouting is active; high-mastery Astral Projection practitioners can detect Vessel position from beyond direct sight.
Integrity affects specific gameplay options available to each player per CVD §17.4 canonical. The 5-band integrity classification surfaces gameplay variation; path-specificity does not gate access to the mode.
Battle Royale framing in canonical lore: ancient survival trials. The closing zone is negative consciousness spreading across the battlefield — thematically consistent with CVD §2 substrate framing rather than arbitrary mechanic.
Full environmental manipulation is active. Players engage the canonical ability tree, weapon framework, and trade infrastructure within Battle Royale match scope.
Match formats: solo, squad (2 players, 3 players, 5 players), guild matches up to 50 versus 50\.
Multiple zone types coexist within the Tier C MMO world layer:
Territorial control persists per §10. Integrity affects kill consequences canonically: L1 Truly Good players killing in non-justified contexts experience canonical integrity drift; L5 Pure Evil players killing operate within canonical cold-violence framing.
Sanctuary zones are canonical no-PvP regions surrounding major crafting and trade hubs. Sanctuary zones operate per Tier C MMO universal canonical rule — applies to all server players regardless of guild integrity, faction standing, or individual integrity band.
Sanctuary zone canonical rule serves the player-driven economy per §11. Crafting and trade hub access cannot be gated by territorial conflict. Sanctuary zones are distinct from Tier B catalog protection per §3.2 — sanctuary zones operate within Tier C scope; Tier B catalog regions are wholly outside Tier C scope.
Tier C MMO bounty system operates independently of integrity-band classification. Bounties are placed by specific NPCs, factions, or players based on specific grievances — not on general moral alignment. A L1 Truly Good player can carry a high bounty if they have specifically wronged a faction; a L5 Pure Evil player may carry a low bounty if they have specifically allied with most factions.
Pure Evil terminal-band (L5) players who conquer and hold territory to create personal safe zones are under constant siege from that point forward, generating enormous bounties and attracting the most capable players on the server. This is canonical opt-in extreme — the L5 path commits to constant defensive engagement.
---
Territory control operates through four documented canonical phases. Guilds and coalitions complete all four phases to establish and maintain territorial control. Losing any phase to a competing faction initiates a defensive response requirement before territorial progress degrades.
Specific phase mechanics, territory map granularity per region, and per-region control rule variations are canonical at framework level here; numerical calibration and per-region implementation defer to Tier C build phase.
Guild canonical architecture:
Multi-guild coalitions form for continental-scale territory control. Council systems are established by the player community, not imposed by the game. The canonical principle: server collective scale per CVD §13.3 emerges from player community organization, not from canonical-mandated structure.
Coalition guild integrity calculates by aggregating constituent guild integrity scores at the coalition canonical level. Specific coalition integrity calculation defers to Tier C build phase.
Guild-controlled territory hosts canonical infrastructure types:
Specific infrastructure mechanic detail defers to Tier C build phase. Canonical principle locks at v1.0.
Tier B catalog regions are excluded from territorial control per §3.2 plus §7.4. Guilds cannot declare territorial control over Tier B catalog regions. Tier B catalog regions retain Tier A canonical-state substrate through all server states.
---
The in-game economy is player-driven within the framework of the trade skill system per T1\_Trades\_Master canonical authority. Scarcity is real because materials are specific to geographic regions and require physical presence to obtain.
Materials specific to each of the 77 Tier A regions plus Tier C regional content create genuine trade dependencies between player communities. Tier C regional materials emerge from Tier C build phase content authoring; canonical principle locks here.
Trades are interdependent at the system level per T1\_Trades\_Master canonical. Engineering trade requires materials from Mining; Alchemy requires Herbalism inputs; Blacksmithing requires Mining. Players who specialize trade with those who specialize differently — or master multiple trades themselves. The economy framework rests on this interdependence.
Tier C MMO scale amplifies trade interdependence — server-wide material flow operates beyond individual player solo region constraints.
Scarcity and value are determined by genuine supply and demand, not arbitrary game inflation. The canonical principle: Tier C economy operates on real material flow with real geographic constraint, not on inflation-correcting game-mechanical loot drop adjustment.
Auction house provides formal player market infrastructure across Tier C MMO scope. Sanctuary zone canonical rule per §9.4 binds auction house geographic placement — auction house terminals operate within sanctuary zones. Specific auction house mechanic detail defers to Tier C build phase.
Bounty system operates per §9.5 canonical independence from integrity-band classification. Bounties posted by specific NPCs, factions, or players based on specific grievances. Bounty hunters claim bounties through canonical kill confirmation; bounty payment routes through auction house infrastructure per §11.4.
---
Per CVD §17.5 hard line: Tier 10 Magus requires Tier C MMO endgame engagement. Tier A solo path caps at Magister Templi.
The hard line is non-negotiable. Magus tier in any developable capability requires Tier C MMO engagement. Tier A solo completion alone produces Magister Templi (Tier 9\) ceiling per CVD §17.5.
Canonical Magus tier prerequisites in any developable capability:
All four elements canonical. Numerical specification for engagement floor and cross-server cooperation count defers to Tier C build phase calibration.
Per CVD §12.1: Magus tier earned through continuing Tier C MMO collective action plus cross-server prestige path. The cross-server prestige path canonical principle: Magus tier engagement spans server boundaries; per-capability Magus questline content involves cross-server cooperative completion.
Specific cross-server prestige path mechanic — server federation architecture, cross-server character recognition, cross-server cooperative quest gating — defers to Tier C build phase engineering specification.
Per CVD §12.1 detail pointer, per-capability Magus initiation questline content authority distributes:
T1\_Tier\_C\_MMO\_Spec owns the Tier C MMO architecture side: engagement floor, guild requirement, cross-server prestige path mechanic. Per-capability Magus content lives in the respective T1 docs.
Magus tier prerequisites are path-agnostic per CVD §17.4 canonical. Pure Evil guilds (L5) earn Magus same as Truly Good guilds (L1). Path-specificity surfaces in capability content (Magus signature manifests differently per integrity band) not in unlock or access requirements.
Canonical principle: integrity-band-canonical content variation operates at content surface level; canonical mastery progression operates at structural level. The two layers are distinct.
---
Per CVD §11.4 canonical. The 12 canonical SQ buckets exhaust Tier A Solo Base canonical content. Beyond the canonical 12, Tier C MMO supports infinite SQ generation through documented-cultural-substrate templates.
Any documented folklore, ritual, mythology, or historical anomaly per region can spawn an SQ instance in Tier C scope. The 12 canonical SQs anchor the substrate; Tier C MMO infinite SQ generation extends the substrate procedurally with documented-source provenance per generated quest.
The canonical principle preserves cultural depiction discipline: Tier C SQ generation respects culture; documented-source provenance binds every generated quest; cultural depiction standard per CVD §6 applies in Tier C identically to Tier A.
Tier C SQ generation operates through documented-cultural-substrate templates organized by canonical SQ bucket structure. Each of the 12 canonical SQs provides the substrate template for infinite Tier C SQ generation in that bucket:
Generated quest content authors at Project 4 Quest Writing scope per Pipeline §6. Batch-level cultural authenticity audit per Pipeline §6.8 binds generated content discipline.
Documented-source provenance is the prerequisite ONLY for generated content that depicts a living culture — its tradition, ritual, language, or sacred practice. Every Tier C generated SQ that depicts a living culture carries documented-source provenance metadata, routed through T0\_Source\_Material\_Registry per Pipeline §8 Book Processing canonical infrastructure; for living-culture depiction, Tier C SQ generation cannot operate on undocumented or speculative cultural material, and documented-source provenance is canonical prerequisite per CVD §6. Fantasy, monster-hunt, vril-combat, dungeon, bounty, and pure-gameplay SQ generation is NOT gated on ethnographic sourcing and generates freely — grounded in a tradition's own material where it draws on one, but free to extrapolate for playable spectacle. This unblocks the bulk of infinite-quest generation while holding the living-culture floor exactly.
Tier A 12 canonical SQ content per T5.13 through T5.24 SQ\_Detailed docs is foundational. Tier C infinite generation extends but does not replace canonical SQ content. Tier C generated SQs reference canonical SQ arc lore where applicable; Tier C generated SQs do not contradict canonical SQ resolution per CVD §17.6 hard line.
---
May 10, 2026\. T1\_Tier\_C\_MMO\_Spec v1.0 ACTIVE authored at Phase 5 Session 5J per T99\_Phase\_5\_Closing\_Sequence\_Handoff §4.2. Concept-locking session scope: three-tier architecture canonical clarification, Tier C scope by exclusion, scale-of-impact framework, guild integrity calculation, regional substrate shaping, Tier C World Boss canonical separation from Tier A 5 chapter-level Boss encounters, competitive multiplayer modes architecture, territory control framework, guild systems framework, player-driven economy framework, Magus mastery tier Tier C architecture, Tier C SQ infinite generation framework. Pre-restructure GDD\_Systems §6 absorbed. Pre-restructure GDD\_Systems §5 World Boss framework absorbed for Tier C scope; Tier A 5 chapter-level Boss encounters owned by T1\_Combat\_System\_Spec §7 per 5H lock.
Six drift items resolved during 5J authoring per CVD §19 protocol. CVD canon wins on every conflict per CI v4.1-Restructure authority hierarchy.
Drift 1 — MMO Layer terminology reframed to Tier C MMO canonical throughout target. Pre-restructure §6 MMO and Multiplayer Systems Framework terminology flattened the canonical three-tier separation.
Drift 2 — Scale-of-impact framing reconciled to CVD §13.3 three-scale canonical (solo, guild collective, server collective). Solo guildless player engagement permitted; solo regional substrate shaping prohibited per canonical principle.
Drift 3 — Infamy and renown scale references reframed to CVD-canonical 5-band integrity (L1 Truly Good through L5 Pure Evil terminal). Pre-restructure §6.4 Infamy Tier 5 players reframed to L5 Pure Evil terminal-band. Bounty system independence preserved.
Drift 4 — Two-layer world framing reframed to canonical three-tier (Tier A Solo Base, Tier B Solo DLC, Tier C MMO). Pre-restructure §4.1 solo region layer plus MMO shared world layer mapped to canonical tiers.
Drift 5 — World Boss scope ambiguity resolved per CVD §13.1 two-scale separation. T1\_Tier\_C\_MMO\_Spec owns Tier C 100-player World Boss roster framework. T1\_Combat\_System\_Spec §7 owns Tier A 5 chapter-level Boss encounters at Ch 8, Ch 23 or Ch 25, Ch 38, Ch 55, Ch 65\.
Drift 6 — World Boss Roster ownership routing absorbed into post-restructure structure. T1\_Tier\_C\_MMO\_Spec owns canonical framework; per-region Tier C World Boss content authoring at Phase 6+ build cascade per CVD §1 build sequence.
July 27, 2026\. The ruled combat-program addendum per docs/COMBAT\_PROGRAM\_ADDENDUM.md §12 (RULED, Josh 2026-07-26) integrated at §8.7 raid-role taxonomy, §8.8 World Boss operational-team architecture and adaptive boss AI, §8.9 single-player party building as raid training ground, with authority-scope touchpoints at §1.2, §1.3, §2.2, §8.3, and §15. The integration adds no new Tier C mechanic; it recovers, it does not mint. It reads the canonical build-role architecture at group scale and recovers the pre-restructure operational detail for the canonical 100-player World Boss — the four operational teams, their headcounts, and the adaptive boss AI — from docs/original\_predclaude/extracted/GDD\_Humanity\_Game\_Complete.md §10.3 World Boss Design and §13.1 World Boss System — Full Detail, routed here per docs/original\_predclaude/INGEST\_GDD.md §13. Two items carry forward. The §8.8 reconciliation registers the cut-line variance between the §8.3 four-team framework and the recovered four-team partition for Tier C build phase resolution; §8.3 stands unchanged in the interim. Seed headcounts, adaptive-AI weighting magnitudes, and sweep thresholds defer to Tier C build phase and to Phase 5M and 5H per §1.5.
---
CVD §1, §2, §6, §9, §11.4, §12.1, §12.4, §13, §17.1, §17.4, §17.5, §17.6 — canonical foundation authority.
T1\_Combat\_System\_Spec v1.0 — Tier A 5 chapter-level Boss encounters separation per CVD §13.1.
T1\_Trades\_Master v1.0 — per-trade Magus lineage content authority per CVD §12.1.
T1\_Ability\_Tree — ability-Magus signature unlock authority per CVD §12.1.
T1\_Integrity\_Paths\_Worldstates\_Master v2.0 — 5-band integrity framework consumer interface; §8.11 companion and familiar build architecture (loadout parity, investment protection, ally stat spreads, the ally-intelligence axis) consumed at §8.7 through §8.9 as the single-player side of the shared role, stat, and build architecture.
T1\_Combat\_System\_Spec and T1\_Ability\_Tree — endgame build-role taxonomy, bonus pools, loadout sets, rarity ladder, six-attribute progression, and the build-space sweeps per docs/COMBAT\_PROGRAM\_ADDENDUM.md §§9-11; read at group scale by §8.7 and §8.9 and not restated here.
docs/COMBAT\_PROGRAM\_ADDENDUM.md §12 — the MMO bridge ruling (Josh, 2026-07-26) integrated at §8.7 through §8.9 per §14.3.
docs/original\_predclaude/extracted/GDD\_Humanity\_Game\_Complete.md §10.3 World Boss Design and §13.1 World Boss System — Full Detail — the authored source of the world-boss four-team architecture, the per-team headcounts, and the adaptive boss AI, recovered into Tier C framework scope at §8.8.
docs/original\_predclaude/INGEST\_GDD.md §13 — the routing record classing that four-team architecture and adaptive boss AI as recovered detail whose home is this doc.
T1\_Vril\_and\_Magic\_System\_Master v2.0 — vril substrate physics consumer interface.
T1\_World\_Geography\_Master v2.0 — canonical 77-chapter region roster for Tier C scope-by-exclusion calculation.
T1\_Tier\_B\_DLC\_Catalog — Tier B pre-identified region catalog authority (populate target post-cascade phase).
T1\_Build\_Pipeline\_Contracts v1.0 ACTIVE — Pipeline §1 UE5, §3 AIVA, §4 ElevenLabs, §6 Quest Writing, §7 Region Page Build, §10 SFX consumer interfaces.
T0\_Boss\_Encounter, T0\_Antagonist\_Network\_Registry, T0\_Quest\_Seed\_Registry, T0\_Cross\_Cultural\_Link\_Graph, T0\_Source\_Material\_Registry — Tier C consumer registry interfaces per Tier C build phase population.
T99\_Phase\_5\_Closing\_Sequence\_Handoff §4.2 — 5J session source authority.
T1\_Architecture\_and\_State — phase plan and architectural canon Drive-only reference.
---
End of T1\_Tier\_C\_MMO\_Spec.